Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1164

reference
651-tree-1
name
1164
tree-preservation-order

undefined

651-tpo-1
uprn
address-text
point
POINT (-1.011945 50.865439)
geometry
MULTIPOLYGON (((-1.011889 50.865433,-1.011891 50.865444,-1.011899 50.865454,-1.011911 50.865462,-1.011927 50.865467,-1.011945 50.865469,-1.011962 50.865468,-1.011978 50.865463,-1.011991 50.865455,-1.011999 50.865445,-1.012002 50.865434,-1.012000 50.865423,-1.011992 50.865413,-1.011980 50.865404,-1.011964 50.865399,-1.011946 50.865397,-1.011929 50.865399,-1.011913 50.865404,-1.011900 50.865412,-1.011892 50.865422,-1.011889 50.865433)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL